Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add logs for GSB http proxy #3304

Merged
merged 6 commits into from
Sep 9, 2024

Conversation

nieznanysprawiciel
Copy link
Contributor

@nieznanysprawiciel nieznanysprawiciel commented Sep 6, 2024

@nieznanysprawiciel nieznanysprawiciel requested a review from a team as a code owner September 6, 2024 11:40
@prawilny prawilny self-requested a review September 9, 2024 09:21
@@ -53,9 +53,9 @@ impl GsbToHttpProxy {

pub fn bind(&mut self, gsb_path: &str) -> Handle {
let this = self.clone();
bus::bind(gsb_path, move |message: GsbHttpCallMessage| {
bus::bind_with_caller(gsb_path, move |caller, message: GsbHttpCallMessage| {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do I understand correctly that it aims to resolve golemfactory/ya-runtime-ai#105?

If so, how does it solve the problem if we don't make use of that parameter in pass() apart from logging? Or do we only want to log the messages for now and fix it after collecting more data?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It doesn't. The problem mentioned is solved here: 27f9350

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or do we solve the problem by switching authorize_activity_executor() to authorize_activity_initiator() and log to ensure that there are no problems with it after the change?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes it's solves the problem with spam that reports incorrectly that something is wrong when it isn't.
I don't want to block possibility of using other yagna as proxy, so the call is not rejected even if it is from incorrect identity

@prawilny prawilny self-requested a review September 9, 2024 12:48
@nieznanysprawiciel nieznanysprawiciel merged commit 7b1f1c0 into gamerhash/master Sep 9, 2024
42 checks passed
@nieznanysprawiciel nieznanysprawiciel deleted the logs/report-http-proxy-calls branch September 9, 2024 12:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants